feat(content-drive): add Action Center for bulk workflow actions - #36821

Draft of the Action Center: a dialog for acting on a multi-item selection,
opened from the toolbar once more than one contentlet is selected. Built
with PrimeNG (accordion, radiobutton, badge, message, skeleton) and
Tailwind for layout only.

Quick Actions fires system actions over the whole eligible selection in
one request. Counts are derived client-side from row state, and an action
that applies to nothing is omitted rather than shown as "(0)".

Workflow Actions renders one collapsible panel per scheme from the bulk
actions endpoint, with real per-action eligibility counts. Steps are
flattened into a single list per scheme, since the step grouping is a
backend detail the dialog does not need to surface.

Scope limits, all deliberate:

- One action per execute. No endpoint fires several different actions in
  one call, and firing one moves contentlets to a new step, which
  invalidates the other counts. The legacy JSP dialog works the same way.
- Actions needing extra input (push publish, move path, assign/comment)
  are disabled with a tooltip rather than reimplementing the params
  dialog. Conditional counts render as "<= N".
- Lock/Unlock and Add to Bundle are omitted: neither has a bulk REST
  endpoint. Legacy drives unlock through a Struts command that loops
  server-side, and add-to-bundle through a legacy AJAX servlet.
- Fires synchronously. Legacy uses the SSE endpoint for live progress,
  which is the better path for large batches but needs an SSE shim.
- Folders are excluded from every payload, matching the endpoints.

System Workflow is intentionally left visible: hiding it would remove
bulk Copy entirely (it has no system-action mapping) and would empty the
section on Community, where it is the only scheme that can exist.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Addresses design feedback on the dialog shell.

The Action Center now owns its own p-dialog instead of rendering inside
the shell's shared one. That shared dialog gives a title and a scrolling
content area; this dialog needs a custom header, a custom footer, and a
body that is the only scrollable region. Two constraints forced the split:

- PrimeNG queries `#header` / `#footer` with `descendants: false`, so the
  templates must be direct children of `p-dialog` and cannot sit inside
  the shell's `@switch` over dialog types.
- Providing a `#footer` template on the shared dialog would render an
  empty footer for the folder and content-type dialogs.

The shell routes ACTION_CENTER out of the shared dialog's content switch
and mounts the component as a sibling instead, keeping the store as the
single source of open/close state.

Layout changes:

- Header carries the title and the selected-contentlet count.
- Footer carries the "one at a time" hint and Done, pinned.
- Content area is `p-0 overflow-hidden` via `pt`; an inner div owns
  `max-h-[60vh] overflow-y-auto`, so only the body scrolls.
- Quick action rows are plain buttons styled with Tailwind to match the
  design: a Material Symbols icon chip, left-aligned label, count and
  chevron trailing, red chip and label for destructive actions. They were
  p-buttons before, which centered their content and could not express
  the chip.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Restyles the dialog against the prototype in
remix_-content-drive/components/ActionCenterDialog.tsx.

The prototype's raw palette is mapped onto the theme tokens that
tailwindcss-primeui exposes — `surface-*`, `primary-*`, `border-surface`
— rather than copying its `slate-*` and hardcoded `#1D1B4B` / `#1D4ED8`
values, so the dialog follows the active PrimeNG theme.

- Fixed-height flex column (`80vh`, `42rem` wide) with the content area
  flexing and scrolling. Replaces the `max-h-[60vh]` guess on an inner
  div; this is how the prototype does it and it keeps header and footer
  pinned without a second scroll container.
- Card treatment: sections sit on `surface-50` inside a rounded-xl
  `surface-100` border, and rows lift to `surface-0` on hover. This was
  inverted before (white card, grey hover).
- Row metrics from the prototype: `gap-4`, `py-3.5`, 20px icon glyphs,
  `size-9` chips with `shadow-sm`, 10px bold section labels.
- Scheme panels are now single-expand, matching the prototype: opening one
  collapses the rest, and the expanded scheme's name takes the primary
  colour. Collapsing a panel clears its pending action so Execute cannot
  stay armed for a hidden panel.

Two deliberate deviations from the prototype, both carried over from the
endpoint analysis:

- Steps use radio semantics, not checkboxes. The prototype multi-selects
  steps, but no endpoint fires several actions in one call and firing one
  moves contentlets to a new step, invalidating the other counts.
- No per-step icon chips. The prototype hand-picks a glyph per step; the
  API returns dotCMS icon names that do not map to Material Symbols, so
  there is nothing to render faithfully yet.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

A collapsed scheme panel in the Action Center still took up the height of
its expanded content, leaving a large blank gap under the header.

PrimeNG 21 collapses accordion content by animating the motion wrapper's
`grid-template-rows` to `0fr`, but that wrapper is configured with
`hideStrategy: 'visibility'` and `unmountOnLeave: false`, so it stays
mounted and keeps its layout box. Without `overflow: hidden` the content
simply overflows the zero-height grid row and the panel keeps its full
height. PrimeNG's own stylesheet only ever sets `grid-template-rows: 1fr`
on `.p-accordioncontent .p-motion`, so nothing clips it by default.

Fixed with the same `pt` override already used by
dot-page-scanner-a11y-report:

    { motion: { root: { style: { overflow: 'hidden' } } } }

Also adopts that component's `dt` content-padding reset so the rows own
their padding, which restores the design's full-bleed dividers, and makes
`[multiple]="false"` explicit rather than relying on the default.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

The scheme panels rendered as borderless grey cards. A `border` utility on
the panel had no effect: the theme ships `accordion.panel.border.width` as
`0 0 1px 0` — inter-panel dividers, which suit one stacked accordion — and
its runtime-injected CSS wins over a utility class.

Overriding the design token instead gives each panel a real border, which
is what the design shows: the schemes are separate cards separated by a
gap, not a stack.

    panel: { borderWidth: '1px', borderColor: '{surface.200}' }

The content section also gets a top border so an expanded header is
separated from its rows, and its background moves to the token rather than
a utility on an inner div, keeping one source of truth per surface.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Gives the scheme panels the same radius and background treatment as the
Quick Actions list, and fixes the reason they did not match.

`p-accordion-panel` exposes only a `value` input — it has no `styleClass`
— so the `rounded-xl bg-surface-50 overflow-hidden` attribute on it was
inert. It has been doing nothing since the panels were introduced; the
grey came from the theme's header background, not from that class. Panel
styling now goes through the `panel` pass-through section, where
`overflow: hidden` is also what clips the header and content corners to
the panel radius.

This also corrects the reasoning in 2a4ebf1: the panel border did not
lose a specificity fight with the theme, the class was never applied at
all. Overriding `accordion.panel.border.*` remains the right fix, since
the theme's `0 0 1px 0` default is meant for a stacked accordion.

Header backgrounds now come from tokens and mirror the Quick Actions rows:
`surface-50` at rest, white on hover, and white while expanded so the open
scheme reads as the active card.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…hrough

Applies the scheme panel's radius via `p-accordion-panel`'s `pt.root`
instead of the parent accordion's `pt.panel`, keeping the override on the
component it targets. Also drops a stray unused `PanelClasses` import.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…ck actions visible

Two pieces of design feedback.

**Renamed to "Workflow Center"** and dropped the toolbar button's icon. The
button and the dialog header share one message key, so the label change
covers both and they stay consistent.

**Quick actions are no longer filtered out when they apply to nothing.**
Every action is always listed; a count of 0 now means "does not apply to
this selection" and the row renders non-selectable, with a tooltip saying
so. Previously such rows were dropped, which made the list shift as the
selection changed — rows appearing and disappearing under the pointer, and
no indication that an action existed but was unavailable. An empty result
still means there are no contentlets at all, where nothing could apply.

Note this makes the count honest rather than decorative: a disabled row is
the one place the UI admits an action is unavailable for the whole
selection, which the previous behaviour hid entirely.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Puts Unarchive back, positioned after Delete so the two archived-only
actions sit together and Add to Bundle stays last.

Without it, archiving was a one-way trip: Archive shows for items that are
not archived and Delete for items that are, but nothing in the dialog could
un-archive. Unarchive is a valid SystemAction the multi-contentlet fire
endpoint accepts, so it needs no extra plumbing.

Order is now Publish, Unpublish, Archive, Delete, Unarchive, Add to Bundle,
asserted by the fixed-order test.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Addresses the PR review.

**Quick actions fired over the whole selection while the row showed only
the eligible count.** `onExecuteQuickAction` built its payload from
`toContentletInodes($selectedItems())`, but the badge came from
`filter(eligibleWhen).length` — two independent derivations. A Publish
reading "(1)" would publish two items, and Delete would be attempted on
contentlets that are not archived.

The eligible inodes are now derived alongside the count in a single filter
pass and carried on the action as `eligibleInodes`, which is exactly what
gets fired. One source, so the number shown and the items touched cannot
drift apart. The success toast reports the same set.

Two regression tests lock this down: one asserts Publish sends only the
non-live inode, another parses the count out of the rendered row and
asserts the fired payload has that many inodes. The previous spec asserted
the buggy payload, which is why this passed review-less.

Also from the review:

- Errors now go through `DotHttpErrorManagerService.handle()` instead of a
  bespoke toast plus `console.error`. Beyond the documented anti-pattern,
  it matters here: per-item permission failures are an expected outcome of
  these endpoints, and the manager distinguishes 401/403 rather than
  flattening everything into one message.
- `getQuickActions` is fed `$contentlets()` rather than re-deriving folder
  exclusion from the raw selection.

New specs for the three untested seams: `getBulkActions` (inode and query
variants, plus the null-entity fallback), the toolbar's Workflow Center
gating and dialog wiring, and the shell's ACTION_CENTER routing including
that the shared dialog stays hidden while it is active.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…-workflow-actions-with-one-action-per-execution